Here is a list of the know issues with the ASLM 1.1GM
---------------------------
Installing over 1.1f1 through 1.1f4
If you try to install over one of the 1.1 "f" builds, the installer will tell you that there is already a newer version installed. Either remove the Shared Library Manager file from the extensions folder first to avoid this dialog or just do a custom install.
-------------
heap=HOLD bug
Using the Library heap=HOLD option in the .exp file can potentially cause problems. The problem is that the memory is never unheld when the library is unloaded. If you repeatedly load and unload your library then eventually most real memory in the system may become held, which would cause a lot of VM thrashing. You are advised to avoid ever unloading your library if you use memory=HOLD and VM is turned on.
-----------------------
THashList and TArray bug
THashList and TArray should have been given an IsValid method because a memory allocation made by their constructors could potentially fail which would cause a crash the first time the THashList or TArray object is used. The easiest way to avoid this problem is to create a subclass that implements the IsValid method. In the case of TArray is should return false if the fArray field is NULL and in the case of THashList it should return false if the fTable field is NULL.
Another alternative is not make sure that their is enough memory in the pool for both the object and the memory it's constructor will allocate. Use the following code for TArray to do this:
NOTE: the following code is meant for demonstration purposes only. The algorithm is sound but no attempt was made to make sure it compiles.
The same code will also work for THashList except that you should use sizeof(THashList) instead of sizeof(TArray).
Note that if someone might allocate memory out of your pool at interrupt time then the above code would not be safe because the memory you allocated to make sure that there was enough could be allocated by an interrupt after the Free() calls but before the you try to allocate the object. In this case you are advised to use subclassing instead.
------------------------------------------
Bug with MacSNMP AppleTalk Transport agent
The MacSNMP AppleTalk Transport agent will crash if ASLM 1.1 is installed. Please read the information in the "MacSNMP Users Read Me!" document on the installer disk for more details and a workaround for the user, and please include this file on your own ASLM Installer disk in case any of the users of your product also use MacSNMP.